feat(container): update image ghcr.io/kguardian-dev/charts/kguardian ( 1.14.3 ➔ 1.16.0 ) - #2477
Conversation
konflate — summaryNote +0 added · 0 changed · −0 removed — 0 resources Caution 1 render failure
konflate · rendered |
![clanker-claude[bot]](https://avatars.githubusercontent.com/in/2839309?s=60&v=4){kind=small}
There was a problem hiding this comment.
ghcr.io/kguardian-dev/charts/kguardian: v1.14.3 → v1.15.0
Verdict: Safe to merge
The chart release adds an opt-in ai.enabled umbrella toggle for the existing llm-bridge, MCP server, and advisor components. It defaults to false, existing component-level flags remain supported, and the chart’s bundled application image versions do not change. This repository sets only controller exclusions and resources, so its rendered workload configuration is unaffected; the release also stops rendering an otherwise-unused llm-bridge ServiceAccount when that component is disabled. No applicable breaking changes or deprecations were found.
New features worth adopting:
ai.enabled— can enable the complete assistant path with one value if that capability is intentionally deployed later. Would changekubernetes/apps/kguardian/kguardian/app/helmrelease.yamland require separately managed provider credentials; no change is needed for this upgrade.
Sources consulted:
- https://github.com/kguardian-dev/kguardian/releases/tag/chart/v1.15.0
- kguardian-dev/kguardian@chart/v1.14.3...chart/v1.15.0
- kguardian-dev/kguardian#1165
- https://github.com/kguardian-dev/kguardian/blob/chart/v1.15.0/charts/kguardian/CHANGELOG.md
- https://github.com/kguardian-dev/kguardian/blob/chart/v1.15.0/charts/kguardian/UPGRADING.md
…( 1.14.3 ➔ 1.16.0 )
c1fd482 to
ee520e3
Compare
robot-rosey
Bot
changed the title
There was a problem hiding this comment.
ghcr.io/kguardian-dev/charts/kguardian: v1.14.3 → v1.16.0
Verdict: Safe to merge
The intervening chart release adds an opt-in ai.enabled umbrella toggle, and v1.16.0 changes llm-bridge to execute MCP tools in-process while updating llm-bridge to v1.4.4. This repository only configures controller exclusions and resources; it does not enable the AI/llm-bridge path or configure the removed single-row traffic endpoint, conversation ID, or broker URL, so no actionable breaking changes or deprecations affect this deployment. The chart also retains the bundled PostgreSQL 15→18 default introduced before this range; no database settings are overridden here, and the repository’s current KGuardian configuration does not consume that database-backed functionality.
New features worth adopting:
ai.enabled— provides a single opt-in switch for the assistant components if that capability is intentionally deployed later; would changekubernetes/apps/kguardian/kguardian/app/helmrelease.yaml.- In-process MCP tools — removes an internal network hop for the assistant path; no repository change is needed while that path remains disabled.
Sources consulted:
- https://github.com/kguardian-dev/kguardian/releases/tag/chart/v1.15.0
- https://github.com/kguardian-dev/kguardian/releases/tag/chart/v1.16.0
- kguardian-dev/kguardian@chart/v1.14.3...chart/v1.16.0
- https://github.com/kguardian-dev/kguardian/blob/chart/v1.16.0/charts/kguardian/UPGRADING.md
- kguardian-dev/kguardian@8126fd4
- kguardian-dev/kguardian@6cc8b57c
- kguardian-dev/kguardian@cacedc4b
1 participant
This PR contains the following updates:
1.14.3→1.16.0Configuration
📅 Schedule: (in timezone America/Chicago)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate.